Inputs for project level quality goals shall be taken from Engineering Quality Goals defined at organization level and Customer specific quality goals, if any, from contract or an equivalent document. Wherever for the same metrics, organization wide defined Engineering Quality Goal and Customer Specific Quality Goal are different, whatever is acceptable shall be taken as a Goal at project level (unless otherwise is explicitly demanded by the customer). Process /Product level quality goals shall be identified before and shared during project kick-off in order to get buy-in/input of all the stakeholders.

Based on experience or any other valid reason, project level goals are taken as different from the Engineering Quality Goals, it shall need an evaluation and explicit approval from the Client Quality Lead and Delivery Manager. Based on organization wide Engineering Goals, sub processes shall be identified based on past performance for their suitability of meeting these goals. (Refer: Metrics Baseline Report and Template for Sub Process Control) Standard metrics set is the comprehensive list of metrics defined in metrics handbook.

A subset of these metrics that is reported by all the applicable projects monthly across the organization and shared with the senior management is known as the Core Metrics set. A slightly bigger set of metrics that contain all the core metrics and some additional milestone/ phase end/ release end metrics is known as the Common Metrics set. Common metrics set at project end and release level is defined in the metrics handbook and mandatory to plan and track through project plan. Additional common metrics at phase end / milestone level is also identified in the project plan. Sub process level metrics and their thresholds shall be identified based on overall target and past performance. The identified Sub process needs to be statistically managed and controlled during the Software development. (Refer: Template for Sub Process Control)

If a goal/metric has been proposed for which baseline (Project past data / Organization) is not available for defining statistical threshold, management or customer-defined threshold shall be used until sufficient data for baseline is collected.

All the quality goals shall be either documented in the project governance plan or quality plan (if it is separate document from project plan) and the same shall be reviewed by QA/CQL as well as other stakeholders and approved by the Delivery Manager.

If a project is not able to meet its defined Quality Targets consistently, it should consider a need for revision of Quality Targets based on the uniqueness of project. Quality targets should be revised and an approval for the same shall be taken from the Delivery head and QA/CQL.

If some new metrics have been implemented at project level successfully, these can be considered for organization level introduction and tracking of metrics after a successful evaluation through piloting or other suitable means and approval by SEPG.

To provide early indicator / warning to project, Q-C-D in-process metrics shall be considered for projects to help them to act at early stages. Refer to Standard RAYG guideline.